Automatic allocation of physical facilities

ABSTRACT

Physical space is allocated to members of a group to maximize collaborative efforts. Each member of the group is determined based on presence or detection of a wireless device. As the members of the group are wirelessly detected, physical space may be assigned based on historical usage, calendar entries, physical needs, and infrastructure traits. Desks, office space, conference rooms, and other facilities may thus be dynamically reserved to maximize collaboration and yet efficiently utilize existing physical spaces.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.14/684,338 filed Apr. 11, 2015 and since issued as U.S. Patent X, whichis incorporated herein by reference in its entirety.

BACKGROUND

Physical space is often wasted. When physical space is allocated to agroup of people, conventional planning allocates the physical space forthe entire group. That is, the physical space is planned for one hundredpercent (100%) capacity. Most times, though, only a smaller percentageof the group is present at any time. People may be absent due tovacation, business travel, training, weather, illness, and many otherfactors. Inefficient allocation of physical space also detracts fromcollaborative efforts, which further introduces inefficiencies.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments areunderstood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIGS. 1-7 are simplified schematics illustrating an environment in whichexemplary embodiments may be implemented;

FIGS. 8-10 are more detailed block diagrams illustrating the operatingenvironment, according to exemplary embodiments;

FIGS. 11-12 are schematics illustrating a database of meetings,according to exemplary embodiments;

FIGS. 13-18 are schematics illustrating locational tracking, accordingto exemplary embodiments;

FIGS. 19-22 are schematics illustrating building services, according toexemplary embodiments;

FIG. 23 is a schematic illustrating elevator summons, according toexemplary embodiments;

FIGS. 24-25 are schematics further illustrating a database of calendars,according to exemplary embodiments;

FIGS. 26-29 are schematics illustrating historical network tracking,according to exemplary embodiments;

FIG. 30 is a schematic illustrating network tracking, according toexemplary embodiments;

FIG. 31 is a schematic illustrating an overall database scheme,according to exemplary embodiments;

FIG. 32 is a schematic illustrating cancelations, according to exemplaryembodiments;

FIG. 33 is a schematic illustrating conferencing activities, accordingto exemplary embodiments;

FIGS. 34-40 are schematics illustrating dynamic assignment offacilities, according to exemplary embodiments;

FIGS. 41-42 are flowcharts illustrating an algorithm for accessauthorization, according to exemplary embodiments; and

FIGS. 43-44 depict still more operating environments for additionalaspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIGS. 1-7 are simplified schematics illustrating an environment in whichexemplary embodiments may be implemented. FIG. 1 illustrates a humanuser 20 in a lobby 22 of a building 24. The human user 20 may be anemployee working within the building 24, or the human may be visitingsomeone within the building 24. The human user 20, in short, may be anemployee, a visitor, a contractor, a tenant, or a guest requesting entryinto the building 24. For simplicity, the human user 20 will mainly bedescribed as a visitor. When the visitor 20 wishes to enter an elevator26 and proceed into secure areas of the building 24, the visitor 20usually must check-in with a security guard. Here, though, exemplaryembodiments detect the wireless presence of the visitor's mobile device30, such as her smartphone 32. That is, if the visitor's smartphone 32is recognized, then exemplary embodiments may permit entry of thevisitor 20 to the secure areas within the building 24. However, if thevisitor's smartphone 32 is unrecognized, then exemplary embodiments mayrequire more authentication credentials or additional measures, as laterparagraphs will explain.

FIG. 2 illustrates wireless presence. When the visitor enters some area(such as the lobby 22 or other area of the building 24), the visitor'ssmartphone 32 may attempt to access a wireless network 40 serving thelobby 22. As the reader likely understands, many people carry asmartphone that interfaces with wireless networks. So, when thevisitor's smartphone 32 enters the lobby 22, the smartphone 32 mayestablish wireless communication with the wireless network 40 servingthe lobby 22. The smartphone 32, for example, may request access orpermission to a local area wireless fidelity (or WI-FI®) network servingthe lobby 22 or any other area.

A security server 42 may be consulted. Once the wireless network 40detects the radio presence of the visitor's smartphone 32, the securityserver 42 may determine whether the visitor 20 is authorized for entry,based on the wireless presence of the visitor's smartphone 32. Forexample, the security server 42 may consult a database 44 of personnel.The database 44 of personnel may store names, addresses, and/or otherinformation for personnel who are authorized to enter the secure area ofthe building 24. The database 44 of personnel, however, may be arrangedaccording to mobile devices. That is, the database 44 of personnel maystore database associations between different names or identities ofpeople and different unique identifiers of their mobile devices. If anentry in the database 44 of personnel matches the unique identifier ofthe visitor's smartphone 32, then the corresponding visitor 20 isauthorized entry. Employees and tenants may thus quickly and easilyenter the building, merely based on wireless recognition of their mobiledevices.

FIG. 3 further illustrates secure access. If the smartphone 32 is notmatched to the database 44 of personnel, the visitor may still begranted access for legitimate purposes. For example, the visitor may bea supplier or contractor attending a meeting within the building 24.When the wireless network 40 detects the frequency presence of thevisitor's smartphone 32, the security server 42 may consult a database46 of meetings. The database 46 of meetings stores different meetingsthat are scheduled or calendared within the building 24. Each meetingmay have an associated list 48 of invitees who are authorized to attendthe meeting. Each invitee, however, may be identified according to hisor her mobile device 30. That is, each invitee may be identified by aunique cellular identifier associated with, or assigned to, theircellular mobile device (such as the smartphone 32). The database 46 ofmeetings may thus store database associations between differentscheduled meetings and different unique identifiers of the invitees'mobile devices 30. If an entry in the database 46 of meetings matchesthe unique identifier of the visitor's smartphone 32, then thecorresponding human visitor may be authorized for entry to attend thecorresponding meeting. Supplier personnel, contractors, and otherinvitees may thus quickly and easily enter the building, based onwireless recognition of their smartphones 32.

FIG. 4 further illustrates the database 46 of meetings. Here inviteesmay be more limited in the dates and times of their access. As FIG. 4illustrates, each meeting 50 may also be associated with a date 52, astart time 54, and a duration 56. Even though the visitor's smartphone32 may be matched as an invitee to the meeting 50, the visitor may stillbe denied access. For example, when the visitor's smartphone 32 requestsaccess to the wireless network 40, a current date and time 58 may betime stamped. If the current date and time 58 does not match thescheduled date 52 of the meeting 50, then entry may be denied.Furthermore, if the smartphone 32 requests wireless access (to thewireless network 40) too early or too late for the scheduled meeting 50,then entry may be denied. The scheduled meeting 50 may thus have awindow 60 of arrival, before or after which the visitor may not enter.So, even though a supplier or contractor is authorized for entry,admittance may be limited to nearly the scheduled date 52 and start time54 of the meeting 50. The user of the smartphone 32 may thus beauthorized for physical entry, but exemplary embodiments may requirethat the user wait until the window 60 of arrival is satisfied.Similarly, when the meeting 50 ends (perhaps at a stop time calculatedusing the duration 56), the visitor's smartphone 32 may not linger.Exemplary embodiments may thus continue tracking the smartphone 32 (aslater paragraphs will explain) during and after the meeting 50 to ensurethe visitor does not afterwards linger too long. If the attendingvisitor lingers too long after the meeting 50, exemplary embodiments maydeny exit from the building, as a security precaution.

FIG. 5 illustrates a database 70 of calendars. Here the visitor'ssmartphone 32 may be matched to an individual employee's electroniccalendar 72. As the reader likely understands, many employees maintaintheir electronic calendars in a central location (such as an enterpriseserver database). The database 70 of calendars, in other words, storesdifferent electronic calendars for different users (such as theemployees and/or tenants in the building 24). When the wireless network40 detects the radio presence of the smartphone 32, the security server42 may query the database 70 of calendars for the unique identifier ofthe smartphone 32. If a matching calendar entry is determined, then thesmartphone 32 is calendared to meet an employee or tenant inside thebuilding. Exemplary embodiment may thus authorize entry, based onwireless network recognition of the visitor's smartphone 32.

FIG. 6 illustrates notification. Once the security server 42 authorizesthe visitor's smartphone 32, electronic notifications may be sent. Thesecurity server 42 may thus generate and send one or more electronicmessages 80 to destination devices 82 associated with differentdestination addresses 84, thus alerting of the visitor's entry into thebuilding. An employee, for example, may be alerted to the visitor'sarrival. Other meeting invitees may also be notified, using the uniqueidentifier assigned to their respective smartphones.

FIG. 7 illustrates entry. Once the security server 42 authorizes thevisitor's smartphone 32, the corresponding visitor may enter the securearea. The security server 42 may thus generate an electronic entryinstruction 86 to allow physical entry. The entry instruction 86 is thensent as packets of data to any destination device. FIG. 7, for example,illustrates the entry instruction 86 routing to a network addressassigned to a lock controller 88. The lock controller 88 manages anelectronic lock 90 securing some door or gate. The entry instruction 86instructs the lock controller 88 to activate or unlock the electroniclock 90, thus allowing the visitor to physically enter the building 24and/or some floor within the building 22. The security server 42 mayfurther instruct an elevator controller 92 to summon an elevator 94,thus lifting the visitor to some floor or level, as later paragraphswill explain. The security server 42 may also monitor or track themovement of the visitor's smartphone 32 to prevent frolic orunauthorized detours (as later paragraphs will also explain).

Exemplary embodiments thus synchronize entry with wireless detection.Wireless detection of any mobile device 30 may thus be used to authorizeentry to secure areas. Even though FIGS. 1-7 primarily illustrate thevisitor's smartphone 32, exemplary embodiments may utilize any wired orwireless device (as later paragraphs will explain). Indeed, badges,watches, and other wearable smart devices may be wirelessly detected topermit access. Integration with personnel directories and calendaringsystems further defines permissible locations of visitors.

FIGS. 8-10 are more detailed block diagrams illustrating the operatingenvironment, according to exemplary embodiments. FIG. 8 illustratespresence detection of the visitor's smartphone 32. When the smartphone32 enters any area, the smartphone 32 may establish wirelesscommunication with the wireless network 40 serving the area. Thesmartphone 32, for example, may request access or permission to a localarea wireless fidelity (or WI-FI®) network, wide area cellular network,or any other network. The wireless network 40 may only recognize, ortransmit/receive, using a particular frequency or band. The smartphone32 may thus instruct its transceiver (not shown for simplicity) towirelessly request access permission using the electromagnetic frequencyband required by the wireless network 40.

The security server 42 may be notified. When the wireless network 40detects the smartphone 32, exemplary embodiments may inform the securityserver 42. That is, the smartphone 32 may send an access request to anaccess device 100 serving the wireless network 40. FIG. 8 illustratesthe access device 100 as a wireless router 102, which commonly servesmany residential and business WI-FI® networks. However, the accessdevice 100 may be any network interface to an access network, such as agateway, cable modem, or DSL modem. Regardless, the smartphone 32broadcasts a request that seeks access permission to the wirelessnetwork 40. When the access device 100 receives the access request, theaccess device 100 may send a packetized access notification 104 into acommunications network 106 for routing and delivery to a network addressassociated with the security server 42. The wireless router 102, forexample, may store or execute code or programming that forces orcommands the access notification 104 when any device attempts to accessthe wireless network 40. The access notification 104 may thus alert thesecurity server 42 to the radio frequency presence of the visitor'ssmartphone 32. The access notification 104 may further includeinformation that uniquely identifies the smartphone 32, such as datarepresenting a cellular identifier 110. While any alphanumericcombination may uniquely identify the smartphone 32, FIG. 8 illustratesthe smartphone's cellular telephone number (or “CTN”) 112, InternationalMobile Subscriber Identity (or “IMSI”) 114, or Mobile StationInternational Subscriber Directory Number (“MSISDN”) 116. Whenever themobile smartphone 32 sends messages or information, the smartphone 32may include or self-report its CTN 112, IMSI 114, and/or its MSISDN 116.

The security server 42 may authorize the smartphone 32. The securityserver 42 has a processor 120 (e.g., “μP”), application specificintegrated circuit (ASIC), or other component that executes a securityalgorithm 122 stored in a local memory 124. The security algorithm 122instructs the processor 120 to perform operations, such as receiving andprocessing information received from a network interface to thecommunications network 106. The information may be received as packetsof data according to a packet protocol (such as any of the InternetProtocols). The packets of data contain bits or bytes of data describingthe contents, or payload, of a message. A header of each packet of datamay contain routing information identifying an origination addressand/or a destination address. The security algorithm 122, for example,may instruct the processor 120 to inspect the packetized accessnotification 104 for the cellular identifier 110 of the visitor'ssmartphone 32 requesting access to the wireless network 40.

FIG. 9 illustrates the database 44 of personnel. The database 44 ofpersonnel may store names, addresses, images, and/or other informationfor personnel who are authorized to enter any area. For simplicity thedatabase 44 of personnel is illustrated as a table 130 thatelectronically maps, relates, or associates different employees ortenants 132 to their corresponding personal information. For example, anentry may associate each person's name 134, address 136, and/or employeenumber 138 to the cellular identifier 110 associated with the person'spersonal wireless device (such as the smartphone 32 illustrated in FIGS.1-8). FIG. 9 illustrates the cellular identifier 110 as the cellulartelephone number 112, the IMSI 114, and/or the MSISDN 116. Each person'swireless device, however, may be additionally or alternatively uniquelyidentified by a network address, a manufacturer's serial number, or anyother alphanumeric combination. Moreover, the database 44 of personnelmay further associate a digital image file 140 to the cellularidentifier 110, thus allowing retrieving, recognition, and/or analysisof a facial image. The database 44 of personnel is illustrated as beinglocally stored in the memory 124 of the security server 42, but some orall of the database entries may be remotely maintained at some otherserver or location in the communications network (illustrated asreference numeral 106 in FIG. 8). While FIG. 9 only illustrates a fewentries, in practice the database 44 of personnel may contain manyentries for hundreds or thousands of people.

The security server 42 may query the database 44 of personnel. When thesecurity server 42 receives the access notification 104, the securityalgorithm 122 causes the processor 120 to query for entries that matchthe query search term(s) detailed or described in the electronic accessnotification 104. If the database 44 of personnel contains a matchingentry, then the security server 42 may authorize the smartphone 32 (andthus the corresponding user or visitor) to enter. The security server 42thus recognizes the smartphone 32 as belonging to one of the personnelauthorized to enter the building (illustrated as reference numeral 24 inFIGS. 1-7). As an example, if the CTN 112, the IMSI 114, and/or theMSISDN 116 detailed in the access notification 104 matches an entry inthe database 44 of personnel, then the security server 42 may concludethat the corresponding user of the smartphone 32 is authorized to enter.

FIG. 10 illustrates the entry instruction 86. When the visitor'ssmartphone 32 matches an entry in the database 44 of personnel, thesecurity server 42 may authorize entry. The security algorithm 122 maythus instruct the processor 120 to generate the entry instruction 86 toallow physical entry. The entry instruction 86 may contain anyinformation that confirms the smartphone 32 is authorized to enter thesecure area. The entry instruction 86 may thus route to the networkaddress assigned to the lock controller 88, thus instructing the lockcontroller 88 to activate or unlock the electronic lock 90. The securityserver 42 may thus unlock a door, gate, or turnstile that permitsphysical entry of the corresponding user of the smartphone 32. Anemployee or tenant thus enters based on the wireless detection of thesmartphone 32.

Exemplary embodiments thus present an elegant solution. In today'smobile environment, people may be uniquely identified by their mobiledevices (such as the smartphone 32). Employees, tenants, and visitorsmay thus be personally identified merely by carrying their smartphones.Exemplary embodiments may thus permit authorized entry to secure areas,simply by recognizing wireless transmissions from their mobile devices.No phone calls are needed, and labor expenses are reduced.

Exemplary embodiments may be applied regardless of networkingenvironment. Exemplary embodiments may be easily adapted to stationaryor mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH®capability. Exemplary embodiments may be applied to mobile devicesutilizing any portion of the electromagnetic spectrum and any signalingstandard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or anycellular standard, and/or the ISM band). Exemplary embodiments, however,may be applied to any processor-controlled device operating in theradio-frequency domain and/or the Internet Protocol (IP) domain.Exemplary embodiments may be applied to any processor-controlled deviceutilizing a distributed computing network, such as the Internet(sometimes alternatively known as the “World Wide Web”), an intranet, alocal-area network (LAN), and/or a wide-area network (WAN). Exemplaryembodiments may be applied to any processor-controlled device utilizingpower line technologies, in which signals are communicated viaelectrical wiring. Indeed, exemplary embodiments may be appliedregardless of physical componentry, physical configuration, orcommunications standard(s).

Exemplary embodiments may utilize any processing component,configuration, or system. Any processor could be multiple processors,which could include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The processor could includea state machine, application specific integrated circuit (ASIC),programmable gate array (PGA) including a Field PGA, or state machine.When any of the processors execute instructions to perform “operations”,this could include the processor performing the operations directlyand/or facilitating, directing, or cooperating with another device orcomponent to perform the operations.

FIGS. 11-12 are schematics further illustrating the database 46 ofmeetings, according to exemplary embodiments. Here the smartphone 32 maybe an invitee to a meeting within some secure area. When the wirelessnetwork 40 detects the radio presence of the visitor's smartphone 32,the access device 100 sends the access notification 105 to the securityserver 42. The access notification 104 may uniquely identify the device(such as the smartphone 32) requesting wireless access, such as datarepresenting the cellular identifier 110 (the CTN 112, the IMSI 114,and/or the MSISDN 116). The security server 42 may then query thedatabase 46 of meetings to determine if the smartphone 32 matches thelist 48 of invitees to any scheduled meeting 50.

FIG. 12 illustrates the database 46 of meetings. For simplicity, FIG. 12illustrates the database 46 of meetings being locally stored in thememory 124 of the security server 42. However, some or all of thedatabase entries may be remotely maintained at some other server orlocation in the communications network (illustrated as reference numeral106 in FIG. 11). While FIG. 12 only illustrates a few entries, inpractice the database 46 of meetings may contain many entries forhundreds or thousands of different meetings or gatherings. The database46 of meetings is illustrated as a table 150 that maps, relates, orassociates different scheduled meetings 50 to the corresponding list 48of invitees. While each invitee 48 may be identified by their name, hereexemplary embodiments identify each invitee 48 according to his or hermobile device identifier. That is, each invitee 48 may be identified bythe unique cellular identifier 110 associated with, or assigned to,their cellular device (such as the smartphone 32). FIG. 12 thusillustrates database associations between a meeting 50, an organizer orinviter 152, and the different invitees 48. Each party to the meeting 50may thus be uniquely identified by their respective CTN 112, IMSI 114,and/or MSISDN 116. Referring back to FIG. 11, if an entry in thedatabase 46 of meetings matches the unique cellular identifier 110associated with the smartphone 32, then the corresponding user may beauthorized for entry to attend the corresponding meeting 50. Thesecurity server 42 may thus authorize entry, such as by generating theentry instruction 86 (as illustrated with reference to FIG. 10).Supplier personnel, contractors, and other invitees may thus quickly andeasily enter the building, based on wireless recognition of theirsmartphones.

FIGS. 13-18 are schematics illustrating locational tracking, accordingto exemplary embodiments. Once the smartphone 32 is authorized forentry, exemplary embodiments may monitor the movements of the smartphone32. If the visitor's smartphone 32 strays or frolics, a security concernmay develop. Exemplary embodiments, then, may track the smartphone 32 toensure the user stays on route to the meeting 50.

FIG. 13, for example, illustrates room assignments. Here the database 46of meetings may also associate a meeting location 154 to each meeting50. As the reader may realize, conference rooms, offices, beveragerooms, and auditoriums may be uniquely identified by some name and/orlocation. So, when the meeting 50 is scheduled or logged in the database46 of meetings, exemplary embodiments may further store an electronicdatabase association with the corresponding meeting location 154.

FIG. 14 illustrates security routings. Once the location 154 of themeeting 50 is determined (from the database 46 of meetings), thesecurity server 42 may query a database 160 of routings. The database160 of routings stores predetermined building routes 162 from somebeginning location (such as a point of entry 164) to the destination atthe meeting location 154. The database 160 of routings, for example, maystore different routes 162 from the lobby of the building (illustrated,respectively, as reference numerals 22 and 24 in FIG. 1) to the meetinglocation 154 of the scheduled meeting 50. FIG. 14 illustrates thedatabase 160 of routings as being locally stored in the security server42, but some or all of the electronic database entries may be remotelymaintained at some other server or location in the communicationsnetwork (illustrated as reference numeral 106 in FIG. 11). A particularconference room, for example, may have a route 162 along which thevisitor is only permitted to walk or navigate. That is, only certainpaths along particular halls and/or through particular doors areavailable to the visitor. The database 160 of routings may thus storeapproved routes 162 along which employees, tenants, and/or visitors maymove from any point (such as the entry 164) to the final destination atthe meeting location 154.

FIG. 15 illustrates GPS tracking. After the visitor's smartphone 32 isauthorized for entry, the visitor should walk or travel along thepredetermined route 162 to the destination meeting location 154. Afterall, confining the visitor to the predetermined route 162 may helpprevent rogue access to unauthorized locations. Exemplary embodiments,then, may track the visitor's position or progress along thepredetermined route 162. FIG. 15 thus illustrates GPS waypoints 170along which the smartphone 32 may or must report. That is, thepredetermined route 162 may be defined as a series of global positioningsystem information. As the visitor walks the corridors of the building,the visitor's smartphone 32 may continually, periodically, and/orrandomly report its current location 172. FIG. 15 illustrates thesmartphone 32 reporting its current location 172 into the wirelessnetwork 40, which the access device 100 may forward to the securityserver 42. The current location 172, however, may be routed into acellular network for delivery to the network address associated with thesecurity server 42. Regardless, when the security server 42 receives thecurrent location 172, the security server 42 may compare the currentlocation 172 to the GPS waypoints 170 associated with the meetinglocation 154. If the current location 172 matches one of the GPSwaypoints (perhaps within a locational tolerance), then the securityalgorithm 122 may conclude that the visitor's smartphone 32 is on trackand proceeding as authorized. However, if the current location 172reported by the visitor's smartphone 32 fails to match one or any of theGPS waypoints 170, the security algorithm 122 may generate a securitynotification 174. The security notification 174 may be any electronicmessage that warns the visitor to resume the predetermined route 162 tothe destination meeting location 154. The security notification 174 mayroute back to the access device 100 for transmission to the networkaddress assigned to the smartphone 32. However, the securitynotification 174 may be a short message service (SMS) text message thatis sent to the unique cellular identifier 110 of the visitor'ssmartphone 32. The security notification 174 may further include acorrection 176 that puts the visitor back on the predetermined route 162to the destination meeting location 154. Moreover, the security server42 may also copy or forward the security notification 174 to a deviceassociated with a security guard for nearly immediate humanintervention.

FIG. 16 illustrates network tracking. Here exemplary embodiments maytrack the current location 172 of the visitor's smartphone 32 usingnetwork recognition. As the reader may understand, GPS signals aresometimes not received in indoor environments. Exemplary embodiments,then, may additionally or alternatively track the current location 172of the visitor's smartphone 32 using network identifiers. FIG. 16 thusillustrates network waypoints 180 along which the smartphone 32 mustrequest access permission. That is, the predetermined route 162 may bedefined as a series of network identifiers. For example, as the visitorwalks the corridors of the building, the visitor's smartphone 32 maywirelessly encounter different wireless fidelity (WI-FI®) networksserving the different floors, hallways, and/or rooms within thebuilding. The visitor's smartphone 32 may also detect other identifiersof other networks (such as different cellular network cells).Regardless, the smartphone 32 may request access permission to eachwireless network 40. The corresponding access device 100 may thus notifythe security server 42 using the access notification 104 (aboveexplained with reference to FIG. 8). FIG. 16, for simplicity,illustrates the network waypoints 180 as a series 182 of service setidentifiers. Each individual service set identifier (or “SSID”) 184uniquely identifiers a different WI-FI® network serving some portion ofthe predetermined route 162 to the destination meeting location 154.When the security server 42 receives each access notification 104, theaccess notification 104 may identify the corresponding SSID 184. Thesecurity server 42 may thus compare the SSID 184 to the networkwaypoints 180 associated with the meeting location 154. If the SSID 184matches one of the network waypoints 180, then the security algorithm122 may conclude that the visitor's smartphone 32 is on track andproceeding as authorized. However, if the SSID 184 fails to match one orany of the network waypoints 180, the security algorithm 122 maygenerate the security notification 174 with the correction 176 (asearlier explained).

FIG. 17 illustrates a strict comparison. As the security server 42receives each access notification 104, the security server 42 mayrequire a strict sequential match with the network waypoints 180. Thevisitor's smartphone 32, in other words, may be required to traverse thenetwork waypoints 180 in sequential order, from a first entry SSID 190to a final destination SSID 192 serving the destination meeting location154. If the visitor's smartphone 32 strays from the predetermined route162, one of the access notifications 104 will identify an SSID 184 notmatching the approved route 162. The smartphone 32, in other words, isrequesting wireless access to an unauthorized network, thus revealing afrolic or detour. The security algorithm 122 may thus alert security (asearlier explained).

FIG. 18 illustrates timing requirements. Here each network waypoint 180may also have a corresponding timing parameter 200. FIG. 18 thusillustrates each network waypoint 182 as an SSID/time pairing. That is,each network waypoint 182 may be a network/timing pair of valuesassociated with each successive wireless network 40. As the visitor'ssmartphone 32 travels along the predetermined route 162, the securityserver 42 may monitor a speed or time of movement. Each accessnotification 104 may have a timestamp 202 that marks a time of requestedaccess to the wireless network 40 (as identified by the SSID 184). Asthe security server 42 sequentially compares the SSID 184 to the networkwaypoints 180, the security server 42 may also require strict adherenceto each corresponding timing parameter 200. The security server 42, inother words, may initialize a timer 204 with receipt of the accessnotification 104. The timer 204 counts up or down to a final value at areceipt of a next access notification 104 associated with the samesmartphone 32 (e.g., the cellular identifier 110). The timer 204, forexample, may thus count a time in seconds or minutes between successiveaccess notifications 104 sent from different access devices 100 alongthe predetermined route 162. So, not only must each sequential SSID 184match the network waypoints 180, but exemplary embodiments may alsorequire timing compliance between the successive network waypoints 180.The security server 42 may thus compare a current value of the timer 204to the timing parameter 200 associated with a next corresponding networkwaypoint 182 along the predetermined route 162. If the current value ofthe timer 204 is less than or equal to the timing parameter 200, thenthe security algorithm 122 may conclude that the visitor's smartphone 32is on the approved route 162 and on track to arrive on time at the finalmeeting destination location 154. However, if the current value of thetimer 204 exceeds the timing parameter 200, the security algorithm 122may conclude that the visitor's smartphone 32 has strayed from thepredetermined route 162. The security algorithm 122 may thus alertsecurity (as earlier explained).

FIGS. 19-22 are schematics illustrating building services, according toexemplary embodiments. Here exemplary embodiments may coordinate or timevarious building services with respect to the location of the smartphone32. As the smartphone 32 travels along the predetermined route 162 (asrepresented by the GPS current location 172, any of the GPS waypoints170, the SSID 184, and/or any of the network waypoints 180), thesecurity server 42 may thus order up or coordinate various buildingservices at appropriate times and locations. FIG. 19, for example,illustrates a database 210 of services. The database 210 of services isillustrated as a table 212 that associates different locations 214 todifferent services 216. As the reader may understand, one of theservices 216 may be lighting requirements 218 for each differentlocation 214. As the user carries the smartphone 32 through hallways andother areas, lights may need to be activated. So, as the security server42 is informed of the smartphone's location 214 along the route 162, thesecurity server 42 may query the database 210 of services for thecorresponding lighting requirements 218.

Lights may thus be defined. The database 210 of services may thus storeelectronic database associations for the lights that illuminate thedifferent locations 214. Each wireless network 40, for example, may bemapped to the light fixtures 220 and/or lighting loads 222 (such asindividual electrical circuits) illuminating its wireless service area.Whenever the security server 42 receives the access notification 104,the security server 42 may thus query for the SSID 184 and retrieve thelighting requirements 218 for its wireless service area. As FIG. 19further illustrates, electronic database associations may be defined forany GPS coordinates or waypoints along the route 162.

As FIG. 20 illustrates, the lights may be activated. Once the securityserver 42 knows the lighting requirements 218 for the location 214, thesecurity server 42 may send a lighting command 230 into thecommunications network 106 for delivery to the network addressassociated with a lighting controller 232. The lighting controller 232responds by activating, or turning on, the corresponding physical lightfixture 234 and/or the physical electrical load 236. The security server42 may thus coordinate the lights along the predetermined route 162 forsafety and security. Lights may then be deactivated when no mobiledevice requests wireless access to the corresponding wireless servicearea. Lights may also be deactivated after some passage of time.

FIG. 21 illustrates HVAC services. Here exemplary embodiments may alsocoordinate heat or air conditioning with respect to the location 214along the approved route 162. As the reader likely understands, as theuser or visitor travels along the predetermined route 162 (asrepresented by the GPS current location 172, any of the GPS waypoints170, the SSID 184, and/or any of the network waypoints 180), thesecurity server 42 may heat or cool the corresponding physical space orarea. Indeed, the security server 42 may even order up an ambienttemperature within the destination meeting location (illustrated asreference numeral 154 in FIGS. 15-16). The database 210 of services maythus include entries for HVAC settings 240 associated with the location214 along the approved route 162. For example, the security server 42may thus query the database 210 of services for the SSID 184 andretrieve the corresponding HVAC settings 240 (such as a temperature 242and/or humidity 244) associated with the corresponding physical space orarea. The security server 42 may then send an HVAC command 246 into thecommunications network 106 for delivery to the network addressassociated with an HVAC system 248. The security server 42 may evenreceive weather data 249 to further analyze and satisfy the HVACsettings 240 desired for the corresponding physical space or area.

FIG. 22 illustrates other services. Exemplary embodiments may alsocoordinate many other services for the comfort and convenience of theinvitees/attendees. The database 210 of services, for example, may alsohave entries for other services, such as network access 250, equipment252, and vending 254. Continuing with the above examples, the securityserver 42 may query the database 210 of services for the SSID 184 of themeeting location 154. The security server 42 may thus retrieve thecorresponding services 216 defined for that meeting location 214. Thesecurity server 42 may then generate a service order 256 that routes toa network address of a service provider system 258. For example, wheneach invitee arrives at the destination meeting location 154, thesecurity server 42 may arrange or prearrange wireless network access 250for each attendee's mobile wireless device. The security server 42, forexample, knows the SSID 184 of the WI-FI® network serving thedestination conference room, along with the unique cellular identifier110 of each attendee's wireless device (as explained with reference toFIGS. 11-14). The security server 42 may thus pre-authorize eachattendee's wireless device with the access device 100 providing wirelessservice in the destination conference room. Each attendee's device thushas immediate access to wireless services.

The equipment 252 may also be ordered. Computers, projectors, conferencephone set-up, pens, and whiteboards are just some of the equipment 252that may be pre-ordered, based on the location 214. The meetingorganizer (illustrated as reference numeral 152 in FIG. 12) may thusenter any data or description of the equipment 252 desired for themeeting. The security server 42 may thus pre-arrange arrival and set-upof the equipment 252. As the attendees enter the destination meetinglocation 154, the equipment 252 they need is automatically ordered andwaiting for use.

Vending 254 may also be pre-arranged. The meeting organizer may thusenter or request any food and drink for the meeting. The security server42 may thus issue orders or commands for on-time delivery of food anddrink from some identified vendor. As the attendees enter thedestination meeting location 154, the requested food and drink isautomatically ordered and waiting for consumption.

FIG. 23 is a schematic illustrating elevator summons, according toexemplary embodiments. As the smartphone 32 moves along the pre-approvedroute 162 to the destination meeting location 154, at some pointelevator service may be required. Exemplary embodiments may thus trackthe smartphone's movement and generate elevator commands at appropriatemoments in time or location. FIG. 23, for example, illustrates anelevator command 270 as a data triplet 271 inserted into one of thenetwork waypoints 180. The elevator command 270 identifies whichelevator (elevator number or identifier) is summoned for vertical travelfrom an entry floor to an exit floor. If a building only has oneelevator, then perhaps the elevator command 270 may be simplified to apair of data values. But many buildings may have multiple elevators,perhaps serving different floors. The elevator command (3, 1, 22), forexample, may call or summon “Elevator #3” to “Floor #1” for lift serviceto “Floor #22.” The opposite elevator command (3, 22, 1) would call“Elevator #3” to “Floor #22” for descend service to “Floor #1.” Eachelevator command 270 may thus be generated for insertion into thepre-determined sequential network waypoints 180. As the smartphone 32satisfied each sequential network waypoint 180, the security server 42may summon the corresponding elevator in the sequence. The securityalgorithm 122 may further initialize the timer 204 to count up or downuntil the summons. Exemplary embodiments, then, may insert the elevatorcommand 270 at appropriate positions and/or times in the sequentialnetwork waypoints 180 and/or the sequential GPS waypoints (illustratedas reference numeral 170 in FIG. 15). As the security server 42 tracksthe smartphone 32, the security server 42 may thus read, retrieve,and/or execute the elevator command 270 as one of the sequential steps.The security server 42 may thus generate an elevator instruction 272that is sent into the communications network 106 for delivery to thenetwork address associated with the elevator controller 92. Elevatorservice may thus be summoned to coincide with the current location ofthe smartphone 32.

FIGS. 24-25 are schematics further illustrating the database 70 ofcalendars, according to exemplary embodiments. When the wireless network40 detects the radio presence of the visitor's smartphone 32, the accessdevice 100 sends the access notification 104 (as earlier explained). Thesecurity server 42 may then query the database 70 of calendars for amatching entry. The database 70 of calendars stores different electroniccalendars for the different employees and/or tenants in the building.FIG. 25, for example, illustrates the database 70 of calendars as atable 280 that maps, relates, or associates different electroniccalendars 72 to different invitees 282. As there may be hundreds ofemployees or tenants, the database 70 of calendars may store a memorypointer or network address to an individual person's electronic calendar72. Regardless, when the visitor's smartphone 32 requests access to thewireless network 40, the database 70 of calendars may be searched orqueried for a matching entry. For example, FIG. 25 illustrates thedatabase 70 of calendars storing electronic database associationsbetween electronic calendar entries 72 and their respective invitees282. Whenever a person schedules a meeting or telephone call, forexample, the invitee may be uniquely identified by his or her uniquecellular identifier 110. An appointment in an electronic calendar, inother words, may be arranged or associated with the CTN 112, the IMSI114, and/or the MSISDN 116 of a participant 282.

The security server 42 may authorize entry. When the security server 42receives the access notification 104, the security server 42 may querythe database 70 of calendars for the visitor's unique cellularidentifier 110. If a matching entry is determined, the security server42 may permit physical entry, as the visitor is scheduled for anappointment with an employee or tenant. If the database 70 of calendarsidentifies the destination meeting location 154, the security server 42may further retrieve and monitor the predetermine route 162 to themeeting location 154 (as this disclosure explains).

FIGS. 26-29 are schematics illustrating historical network tracking,according to exemplary embodiments. Here, historical observances ofwireless detections may be used to infer future actions. That is, auser's habitual usage of the smartphone 32 may be used to predict whereshe will move, and/or what she will do, based on her past wirelessnetwork access. For example, as the smartphone 32 repeatedly moveswithin the building 24, over time exemplary embodiments may makerecommendations and assumptions, based on habitual observance of itsnetwork usage. Whenever the smartphone 32 is detected at some locationor requesting access to any network, exemplary embodiments may matchthat detection to some past occurrence. In other words, most people arecreatures of habit, so exemplary embodiments may predict our futuremovements and actions based on our historical behaviors.

FIG. 26 illustrates a database 300 of usage. The database 300 of usagetracks historical usage of any user's wireless device 30 (such as thesmartphone 32). The database 300 of usage may store entries related tousage at different times of days and/or at different locations. Wheneverthe smartphone 32 reports its GPS current location 172, for example,exemplary embodiments may query the database 300 of usage for historicalusage at that same location. The database 300 of usage may thus log eachcurrent location 172 reported by the smartphone 32. As the smartphone 32moves within the building 24, the smartphone 32 may send its currentlocation 172 (such as GPS information) to the security server 42 forstorage in the database 300 of usage. The database 300 of usage isillustrated as being locally stored within the security server 42, butany of the database entries may be remotely maintained at othernetwork-accessible locations or servers. FIG. 26 illustrates thedatabase 300 of usage as a table 302 that electronically maps, relates,or associates the cellular identifier 110 to different location reports.That is, each time the smartphone 32 reports its current location 172,the database 300 of usage may add an entry for the unique cellularidentifier 110, the reported current location 172, and a date and time304 of the report. Over time, then, the database 300 of usage may storelong-term records of the movements of the smartphone 32 within thebuilding 24.

FIG. 27 illustrates historical network usage. Each time the smartphone32 requests access to the wireless network 40, the corresponding accessdevice 100 sends the access notification 104 to alert the securityserver 42 (as this disclosure earlier explained). The security server 42may thus instruct the database 300 of usage to log the accessnotification 104, perhaps also with the date and time 304. That is, eachtime the smartphone 32 requests wireless access to the wireless network40, the database 300 of usage may add an entry for the unique cellularidentifier 110, the service set identifier (“SSID”) 184 of the wirelessfidelity (“WI-FI®”) network 40, and the date and time 304 of therequest. As FIG. 27 illustrates, the database 300 of usage may merelylog the timestamp 202 reported in the access notification 104, or thedatabase 300 of usage may log some other measure of time (such asreceipt of the access notification 104). Regardless, over time thedatabase 300 of usage reveals a comprehensive long-term centralrepository of network access requested by the smartphone 32.

The security server 42 may thus exploit the historical information. Thesecurity server 42, for example, may query the database 300 of usage forany search terms and retrieve matching historical entries. The securityserver 42, as an example, may query for historical entries associatedwith the cellular identifier 110. The security server 42 may thusretrieve historical locations or networks logged in the database 300 ofusage. Indeed, the security server 42 may even query for historicalentries having the same or approximate date and time 304. The securityserver 42 may thus retrieve historical entries that match the same orsimilar day, time, current location 172, or network SSID 184.

FIG. 28 illustrates locational prediction. Whenever the smartphone 32reports its current location 172, the security server 42 may predict orinfer a future location 310. For example, the security server 42 mayquery for a series or sequence of entries having about the same location172 and/or the same date and time 304. For example, if one or more ofthe smartphone's recent locational reports match one or more historicalentries, then the security algorithm 122 may infer that the smartphone32 is moving along a path historically observed. That is, the smartphone32 is being carried along a familiar route to a historical destinationpreviously logged in the database 300 of usage. In other words, if arecent string or sequence of locational reports matches some sequence ofhistorical entries, then the security algorithm 122 may conclude thatthe smartphone 32 is traveling along the same route to the samedestination. If the smartphone 32 reports the same current locations 172within a ten minute (10 min.) window of time as historically seen, thesecurity server 42 may thus predict or infer that the smartphone 32 willhave the future location 310 that matches at least one of the historicalentries in the same series. As one example, if the smartphone's mostrecent five (5) location reports match some historical observance in thedatabase 300 of usage, then the security server 42 may predict thesmartphone's future location 310 will match the next historical sixth(6^(th)) entry in the same historical sequence. The security server 42may thus query for any search terms and retrieve one or multiplehistorical entries that match recent locational reports. As most peopleare creatures of habit, the security server 42 may thus predict thefuture location 310 of the smartphone 32 based on historicalobservances.

FIG. 29 illustrates network prediction. As the database 300 of usage mayalso log historical network requests, exemplary embodiments may predictor infer a future network 312. For example, the security algorithm 122may predict the smartphone's access request to a wireless fidelity(“WI-FI®”) network, based on the historical entries in the database 300of usage. The security server 42 may query for a series or sequence ofentries having one or more matching SSID 184 entries and/or about thesame date and time 304. For example, if one or more of the recent accessnotifications 104 match one or more historical entries, then thesecurity algorithm 122 may infer that the smartphone 32 is requestingaccess permissions along a path historically observed. In other words,if a recent string or sequence of access notifications 104 matches somesequence of historical entries, then the security algorithm 122 mayconclude that the smartphone 32 is requesting wireless access ashistorically seen. If a string or sequence 314 of the accessnotifications 104 match historical entries within a ten minute (10 min.)window 316 of time, the security server 42 may thus predict or inferthat the smartphone 32 will request access to a next entry historicallyobserved in the same series. As FIG. 29 illustrates, if the recentaccess notifications 104 report the sequence 314 “SSID2, SSID3, SSID4,SSID3,” then the security algorithm 122 may retrieve the next entry inthe same sequence 314 and predict that the smartphone 32 will nextrequest access to “SSID9.” The security algorithm 122, in other words,infers the future network 312 as the next entry in the matching sequence314. The security algorithm 122 may thus pre-arrange wireless access,elevator service, lighting, and other services based on this prediction.

FIG. 30 is another schematic illustrating network tracking, according toexemplary embodiments. Here exemplary embodiments may track usage oraccess requests to any networking environment. As FIG. 30 illustrates,whenever the smartphone 32 requests access to any wireless network 40,the access notification 104 may report the networking details. Theaccess notification 104, for example, may report a radio frequency 320and/or bitrate 322 of communication between the smartphone 32 and someother wireless device. The timestamp 202 may be further added. When thesecurity server 42 receives the access notification 104, the securityalgorithm 122 may thus log these details in the database 300 of usage.For example, the radio frequency 320 and/or bitrate 322 may allow thesecurity algorithm 122 to log whether the wireless network 40 operatesat cellular frequencies or WI-FI® frequencies.

Other networking environments may also be tracked. When the securityserver 42 receives the access notification 104, the radio frequency 320and/or the bitrate 322 may reveal near-field communications and/or radiofrequency identification (“RFID”) communications. For example, when thesmartphone 32 participates in near-field communication, the accessnotification 104 may additionally or alternatively report an initiatordevice 324 and a target device 326. Likewise, the access notification104 may also detail unique radio frequency identification tags andreaders. When the security server 42 receives the access notification104, the security algorithm 122 may thus log these details in thedatabase 300 of usage. Over time, then, the database 300 of usagecontains historical entries detailing the near field and RFIDtransactions involving the smartphone 32. If any current transactionmatches some historical entry, the security algorithm 122 may predict orinfer future actions and/or locations, based on the match. The securityalgorithm 122 may thus pre-arrange wireless access, elevator service,lighting, and other services based on this prediction.

FIG. 31 is a schematic illustrating an overall database scheme,according to exemplary embodiments. Here the security server 42 mayaccess any of the databases (illustrated as reference numerals 44, 46,70, 160, 210, and 300) to authorize access, to coordinate services, andto predict actions, as this disclosure explains. The databases may beindividually maintained or grouped together, depending on networking,processing, and storage capabilities.

FIG. 32 is a schematic illustrating cancelations, according to exemplaryembodiments. Even though the security server 42 may have authorizedaccess, coordinated services, and/or predicted actions, sometimescancelations are determined. For example, a meeting organizer may simplycancel a scheduled meeting in the database 46 of meetings. Thiscancelation 340 may then trickle down and affect access, services, andpredictions. For example, if the cancelation 340 is determined in thedatabase 46 of meetings, the security server 42 may disperse thatcancelation 340. The invitees' devices to the now-canceled meeting maybe notified (perhaps using the notification message 80 illustrated inFIG. 6). Entry authorization for the invitees' devices may be canceledby removal from the database 46 of meetings and/or removal from thedatabase 70 of calendars. The entry instruction (illustrated asreference numeral 86 in FIG. 7) may be canceled, thus stopping orceasing any entry process. The elevator instruction (illustrated asreference numeral 272 in FIG. 23) may be canceled, thus removing anysummons for elevators. Likewise, any retrieval and/or analysis of routesin the database 160 of routings may be canceled or aborted. Anyretrieval and/or electronic order of services in the database 210 ofservices may also be canceled or aborted. Moreover, electronicnotifications of the cancelation 340 may be sent to service providers(such as contractors and vendors). Any historical analysis of entries inthe database 300 of usage may be halted or aborted. The cancelation 340may thus electronically cancel any reservation for a conference room,HVAC needs, and lighting requirements.

FIG. 33 is a schematic illustrating conferencing activities, accordingto exemplary embodiments. Here exemplary embodiments may arrange andset-up a teleconference call and/or a telepresence video call betweenthe visitor's smartphone 32 and other participants. When the visitorarrives, the visitor's smartphone 32 requests wireless access (asearlier explained). The security server 42 may thus use the uniquecellular identifier 110 to retrieve any meeting entries in the database46 of meetings and/or in the database 70 of calendars. The securityserver 42 may arrange a conference room and/or an office or desk for thevisitor, in response to a matching entry. The security server 42 mayalso automatically set-up a teleconference call or a videoconferencecall to the meeting invitee devices retrieved from the database 46 ofmeetings and/or the database 70 of calendars. The security server 42 mayalso concomitantly arrange video cameras, whiteboards, beverages,lighting, and other services (perhaps revealed by the database 210 ofservices, as previously explained).

FIGS. 34-39 are schematics illustrating dynamic assignment offacilities, according to exemplary embodiments. This disclosure explainshow wireless detection of any person's mobile device 30 (such as thesmartphone 32) may be used to make any prediction of location, action,and/or usage. That is, wireless detection of our mobile devices allowsintelligent inferences and predictions of our habits and needs. Forexample, patterns of wireless usage may be used to optimally configurethe locations of retail displays, employee tools, service kiosks,vending machines, and advertising displays. Analysis of wireless accessmay yield insights into group interactions, electronic communicationsand collaboration, prior locational trends, and calendar schedules.Exemplary embodiments may thus predict your daily schedule, your dailymovements (e.g., work and play), friends and coworkers, and youractivities, all based on patterns of wireless access associated withyour mobile devices. As any person or user moves or roams, the wirelessdetection of the mobile device 30 (such as the smartphone 32) may betracked and historically monitored to discern and predict patterns ofrepeated movement and reception. These predictions may thus be used tocorrelate physical and logical interpersonal relationships toautomatically and more effectively assign personnel to specific worklocations on demand, thus maximizing productivity. Opportunities fordynamic innovation, perhaps through face-to-face interaction betweenpeople, are increased, thus allowing architects and building planners tomore accurately and efficiently predict utilization and occupancy trendsfor use in future capacity planning.

Exemplary embodiments thus reveal much information about users. Thedatabase 300 of usage, for example, may log interactions between thesmartphone 32 and other wireless devices. This information thus revealswith whom the user is actually communicating and collaborating acrossboth physical and electronic interactions. These interactions may beused to dynamically optimize physical work environments. Theseinteractions may also be used to accurately adjust physical locations asrelationships change over time. Due to the dynamic nature of today'sglobal business, a person's sphere of interest and required contacts maychange on a regular basis. Some users may have collaborational needsthat change on a daily basis, while other users may have needs thatchange hourly or monthly. Exemplary embodiments may thus dynamicallyreact, regardless of the time frame. These regular or irregular changesmay result in broad changes of an enterprise's voice and data networkservice requirements, including access, bandwidth, and service quality.

Exemplary embodiments may thus utilize big data analytics. As the readermay understand, information is currently generated for every phone call,instant message, email, social media posting, calendar event(s), workproject(s), and audio or video conference (perhaps in both an enterpriseenvironment and in a carrier environment). More data is created on thelocation of a person geospatially depending upon the configuration andcapabilities of their laptop, smartphone, tablet or wearable device.Even though many enterprises and service providers generate and collectthese data, exemplary embodiments add correlation to effect improvementsin user productivity, to increase the opportunity for dynamiccollaboration through face-to-face interactions, and to identify trendsfor capacity planning. For example, exemplary embodiments mayautomatically allocate workspace based on wireless detection of mobiledevices. That is, teams of individuals may be defined by theirrespective cellular identifiers 110. Physical space, and even work desksand conference rooms, may be allocated based on the wireless detectionof their smartphones 32. In other words, office space is automaticallylocated with other team members having the same goals, projects and/ortasks. As projects change over time, physical workplace assignments areoptimally configured to enable regular, consistent, face-to-face andvirtual interactions between team members, according to their uniquecellular identifiers 110. One day the physical space may reduce when fewsmartphones are detected or predicted in advance by analysis, while thenext day the physical space may be expanded when many team members'smartphones request wireless access.

Exemplary embodiments may thus collect electronic data regarding membersof groups. As the members collaborate and communicate, their respectivemobile devices generate electronic data. All this electronic data isconveyed along the wireless network 40 and/or the communications network106 for delivery to different destinations. Any electronic dataassociated with the mobile devices 30 (such as the unique cellularidentifier 110 of their smartphone 32) may thus be used to dynamicallyalter physical building needs. Small conference rooms may thus bescheduled when only a few cellular identifiers 110 are detected. Largerconference rooms are scheduled when many team members are detected.

Usage patterns are also valuable for designers. Over time the databases(illustrated as reference numerals 44, 46, 70, 160, 210, and 300 in thisdisclosure) may reveal long-term historical information that is of valueto architects and other designers. Exemplary embodiments, for example,may reveal that only forty percent (40%) of employees'smartphones aredetected or predicted on any given day. Physical needs may thus besignificantly reduced, as one hundred percent (100%) capacity is notneeded. Indeed, one general all-purpose space (such as an auditorium,cafeteria, lobby, warehouse footage, etc.) may be developed toaccommodate abnormally large gatherings of employees. Alternatively, thesecurity server 42 may sum or tally the predicted or actual number ofdetected wireless devices and automatically reserve or arrange off-sitespace (such as a hotel conference room or school gymnasium). Long termpatterns of wireless detection and usage may also reveal the need forphysical and technological renovations of existing facilities.

Exemplary embodiments may thus adapt to changing times and needs. As thesecurity server 42 monitors wireless detection of mobile devices, floorspace and office equipment become adaptive tools that generate data ontheir health and occupancy. Physical spaces may be dynamically optimizedbased on virtual or electronic interactions as those relationshipschange and evolve. Increasing the probability of face-to-faceinteractions as work locations are assigned enhances the opportunity fordynamic interpersonal innovation. Moreover, exemplary embodimentsimprove real estate planning efforts, thus leveraging actual user datato predict future workplace capacity and utilization patterns. Dependingupon the location and size of the user base, this approach also haspotential impacts on energy utilization, commuter traffic utilization,civil/environmental engineering and employee satisfaction,recruiting/retention, and work-life balance.

FIG. 34 thus illustrates a database 350 of groups. The database 350 ofgroups stores a roster for different groups 352 of employees,contractors, and other personnel. The database 350 of groups, in otherwords, stores the membership of teams, departments, offices, and anyother grouping or organization of people. However the groups 352 ofpeople are organized, the database 350 of groups stores the differentmemberships of those groupings.

Each member, though, is uniquely identified by their mobile device 30(illustrated as the smartphone 32). As each group member enters thebuilding 24, exemplary embodiments may log their presence in thedatabase 350 of groups. That is, when each group member's smartphone 32is wirelessly detected, exemplary embodiments may update the database350 of groups. Exemplary embodiments, for example, may define membershipaccording to each person's unique cellular identifier 110. Eachdifferent group 352, in other words, may be defined according to theunique cellular identifiers 110 of its members. As each member'ssmartphone 32 requests wireless access to the wireless network 40,exemplary embodiments may determine the corresponding membership in oneor more teams, departments, or other groupings.

The security server 42 may query the database 350 of groups. When thesecurity server 42 receives the access notification 104, the securityalgorithm 122 causes the processor 120 to query for entries that matchthe query search term(s) detailed or described in the electronic accessnotification 104. The security server 42 may thus query the database 350of groups for the cellular identifier 110 associated with the personalwireless device 30 (such as the smartphone 32) requesting wirelessaccess to the wireless network 40. If the database 350 of groupscontains a matching entry, then the security server 42 knows that one ofthe members of the group 352 is present in the building 24. The securityserver 42 may then dynamically configure physical facilities, as laterparagraphs will further explain.

FIG. 35 further illustrates the database 350 of groups. The securityserver 42 may query the database 350 of groups. For simplicity thedatabase 350 of groups is illustrated as a table 354 that electronicallymaps, relates, or associates different groups 352 to their correspondingmembership 356. Here, though, each member 356 is defined by the cellularidentifier 110 associated with the member's personal wireless device(such as the smartphone 32 illustrated in FIG. 34). Each member 356,though, may be additionally or alternatively uniquely identified by anyother alphanumeric combination, such as an employee number, a networkaddress, a manufacturer's serial number, or even a name. FIG. 35illustrates the database 350 of groups as being locally stored in thememory 124 of the security server 42, but some or all of the databaseentries may be remotely maintained at some other server or location inthe communications network (illustrated as reference numeral 106 in FIG.8). While FIG. 35 only illustrates a few entries, in practice thedatabase 350 of groups may contain many entries for hundreds orthousands of groupings.

Exemplary embodiments may thus track a wireless presence 358 ofdifferent groups. When any wireless device requests wireless access, thesecurity server 42 may determine its corresponding membership 356 in theone or more groups 352. As FIG. 35 also illustrates, exemplaryembodiments may also track the current wireless presence 358 of thedifferent group members 356. That is, whenever the member's cellularidentifier 110 is matched as one of the group members 356, the database350 of groups may also log that wireless presence 358. Exemplaryembodiments, in other words, may generate a listing 360 of members whohave a physical presence in the building (illustrated as referencenumeral 24 in FIG. 34), as determined by their wireless presence 358.The listing 360 of members, for example, may be a list or string of thedifferent cellular identifiers 110 associated with the members' personalwireless devices requesting wireless access. At any time, then, thesecurity server 42 may query the database 350 of groups and retrieve thelisting 360 of members who are physically present in the building 24, asdetermined by their respective cellular identifiers 110.

Exemplary embodiments may maintain a numerical count 362. As memberscome and go, their respective wireless devices will change theirwireless presence 358. For example, as a member's smartphone accessesthe wireless network (illustrated, respectively, as reference numerals32 and 40 in FIG. 34), the listing 360 of members will increase innumber to reflect an addition of the team member 356. When the memberleaves or exits the building 24, the smartphone 32 leaves or disconnectsfrom the wireless network 40 (e.g., no longer accesses the wirelessnetwork 40), the listing 360 of members may decrease in number toreflect a subtraction of the team member 356. The database 350 of groupsmay thus maintain the current numerical count 362 of the listing 360 ofmembers who are physically present in the building 24, as determined bytheir respective cellular identifiers 110 accessing the wireless network40. Exemplary embodiments may sum the entries in listing 360 of membersto determine the current numerical count 362. At any time, then, thesecurity server 42 may query the database 350 of groups and retrieve thecurrent numerical count 362 of the corresponding group members 356 whoare physically present in the building 24 (as determined by theirrespective cellular identifiers 110).

As FIG. 35 also illustrates, the database 350 of groups may include aphysical space requirement 364. Each different group 352 may haverequirements for its physical space. Some groups, for example, mayrequire a large space to complete their assigned task. A repair group,for example, may require a large physical space to accommodate both themembers and their tools/equipment. Likewise, an engineering group mayrequire a larger physical space to accommodate workstations, designmockups, and collaborative video conferencing tools. A smaller group,with lesser needs, may thus require a much smaller physical space. Eachgroup 352 may thus have its associated physical space requirements 364.

For example, FIG. 35 illustrates a square footage 366. That is, thephysical space requirement 364 may be defined in terms of the squarefootage 366 per member who is physically present. As this disclosurepreviously explained, a group 352 may only have a fraction of its totalmembership present on any particular day. Some members may be onvacation, some may be sick, and some may work off-site. Physical needsmay thus be significantly reduced, as one hundred percent (100%)capacity is not needed. Exemplary embodiments may thus calculate anygroup's physical space according to the square footage 366 per memberwho is physically present. The security server 42 may thus query thedatabase 350 of groups and retrieve the current numerical count 362 ofthe corresponding group members 356 having the wireless presence 358 (asdetermined by summing their respective cellular identifiers 110). Thesecurity server 42 may then multiply the current numerical count 362 bythe square footage 366 per member to determine the physical spacerequirement 364. For example, if five (5) team members are wirelesslydetected, and each member requires sixteen square feet (16 ft²), thenphysical space requirement=(5 members)×(16 ft²/member)=80 ft².As only five (5) team members' devices are wirelessly detected, thegroup 352 only requires 80 ft² of physical space. The group 352, inother words, may only require a small conference room or lounge toaccomplish their assigned task. A larger physical space is likely wastedon such a small wireless presence. A larger physical space, in otherwords, may be reserved for a larger group whose members are wirelesslydetected.

FIG. 36 illustrates a database 370 of physical spaces. Once the securityserver 42 determines the physical space requirement 364 for the members'devices wirelessly detected, the security server 42 may query thedatabase 370 of physical spaces. The database 370 of physical spacesallows the security server 42 to dynamically assign facilities,according to the physical space requirement 364 for the memberswirelessly detected. For simplicity the database 370 of physical spacesis illustrated as a table 372 that electronically maps, relates, orassociates different physical spaces 374 to their corresponding physicaltraits 376. The database 370 of physical spaces, for example, may haveelectronic database associations between different rooms and offices totheir corresponding physical measurements (e.g., such as their squarefootage 378). FIG. 36 illustrates the database 370 of physical spaces asbeing locally stored in the memory 124 of the security server 42, butsome or all of the database entries may be remotely maintained at someother server or location in the communications network (illustrated asreference numeral 106 in FIG. 8). While FIG. 36 only illustrates a fewentries, in practice the database 370 of physical spaces may containmany entries for hundreds or thousands of physical spaces. Regardless,once the security server 42 determines the physical space requirement364 for the members wirelessly detected, the security server 42 mayquery the database 370 of physical spaces and retrieve the physicalspace 374 that matches the physical space requirement 364 for thedetected members. The security server 42 may thus dynamically assign andreserve the physical space 374 that best meets the physical spacerequirement 364 for the members wirelessly detected.

Exemplary embodiments may thus dynamically assign facilities. Again, agroup 352 of one hundred different members 356 may only have twenty (20)present at any time, given different personal and work schedules.Exemplary embodiments thus use wireless detection of each member'smobile device 30 to determine physical needs. Exemplary embodiments maythus dynamically assign desks, workspaces, and other physical needs,based on wireless detection.

FIGS. 37-38 illustrate other physical space requirements 364. As thereader may understand, some groups 352 may have other requirements forits physical space. Some groups, for example, may require at least oneworkstation computer for complex analysis of design parameters. Anothergroup 352 may require video conferencing capability, with a largedisplay for conducting business or research. Still another group 352 mayrequire a special laboratory with special equipment to perform researchactivities. The database 350 of groups may thus further include atextual description 380 of any additional physical space requirements364. As FIG. 38 illustrates, when the security server 42 queries thedatabase 370 of physical spaces, the search term(s) may thus alsoinclude the textual description 380 of any additional physical spacerequirements 364. The security server 42 may thus retrieve the physicalspace 374 that also matches the textual description 380 of anyadditional physical space requirements 364. The security server 42 maythus dynamically assign and reserve the physical space 374 that bestmeets the textual description 380 of the additional physical spacerequirements 364 for the members wirelessly detected. The securityserver 42, in other words, may dynamically assign rooms or labs havingspecialized equipment needed by any group to accomplish their assignedtask.

Exemplary embodiments may also operate as previously mentioned. Forexample, once the security server 42 determines the physical space 374,the security server 42 may retrieve the route 162 to the physical space374 (as explained with reference to FIGS. 14-18). Exemplary embodimentsmay determine any of the services 216 associated with the physical space374 (as explained with reference to FIGS. 19-22). An elevator may besummoned, as explained with reference to FIG. 23. Exemplary embodimentsmay also track network usage and make predictions, as explained withreference to FIGS. 26-29.

FIG. 39 illustrates notification. Once the security server 42 determinesthe physical space 374 for the members wirelessly detected, electronicnotifications may be sent. The security server 42 may thus generate theelectronic message 80 detailing the physical space 374 assigned to thegroup 352. Most likely the electronic message 80 will include digital orelectronic information uniquely describing a desk or room numberassigned to members wirelessly detected. The electronic message 80, forexample, may identify a lounge or conference room selected to satisfythe physical space requirements 364 for the members wirelessly detected.For simplicity, the electronic message 80 may be addressed to the uniquecellular identifier 110 associated with each member's device. Forsimplicity, FIG. 30 illustrates the electronic message 80 routing fortransmission by the wireless network 40 to the smartphone 32 having thewireless presence 358 in the database 350 of groups. Each member maythus be notified of the physical space 374 assigned to the group 352.

Exemplary embodiments may thus dynamically allocate and reserve based onwireless presence. If only a single member of the group needs physicalspace, perhaps only a single desk or office is needed. Exemplaryembodiments, then, may select a desk or office satisfying the locationaland/or equipment needs of the single member. Exemplary embodiments maythus generate an electronic reservation to reserve the desk or officefor the use of the single member. Exemplary embodiments, in other words,may form or generate an electronic database association between themember's unique cellular identifier 110 and a desk number and/or officenumber. A larger physical space may be reserved and electronicallyassociated with a larger group of members' cellular identifiers 110. Thedatabase 350 of groups may thus contain a central repository ofreservations between the members 356 having the wireless presence 358and their assigned, reserved physical space 374.

FIG. 40 illustrates predictive analysis. Now that the architecturalscheme is developed, exemplary embodiments may implement a predictivecomponent to further maximize collaboration and efficiency of physicalspace. For example, as the security server 42 executes the securityalgorithm 122, the security server 42 may also access and execute apredictive module 382. The predictive module 382 has instructions,programming, or code that causes the security server 42 to inferphysical assignments, based on analysis of the electronic data orentries in any of the electronic databases 44, 46, 70, 160, 210, 300,350, and/or 370. The predictive module 382 may thus have access to rulesand other logical relationships defining conditions, parameters, and/orthreshold values for predictive decisions.

Predictive analytics may thus be applied to physical needs. Thisdisclosure explains how each person's mobile device 30 may be trackedand monitored for movements. Moreover, this disclosure also explains howhistorical observances of mobile devices may be used to infer futureactions. Over time, then, the database 300 of usage reveals habitualusage for any mobile device (such as the smartphone 32). Whenever anyperson's mobile device 30 is detected, the security server 42 mayretrieve the corresponding usage pattern and predict future movementsand actions, based on historical or habitual observance. This repeatedobservance thus reveals what mobile devices are typically detected atthe same (or nearly the same) work location. Wireless detection alsoreveals which employees only intermittently work on site (such as thosewho remotely work from home or other facilities). The entries in theelectronic databases 44, 46, 70, 160, 210, 300, 350, and/or 370 revealwhich workers often collaborate, whether or not assigned to the samegroup or team. Exemplary embodiments also know the locations of theseformal or informal collaborations. Exemplary embodiments may thusautomatically assign a typical or formal location for repeatedcollaborative efforts, thus promoting consistency in work location thatfosters successful face-to-face communication. However, the securityserver 42 may determine that a random or different physical location ispreferred, perhaps in an effort to spawn new ideas with new people.

Calendric and locational information may be especially predictive.Whenever mobile devices 30 are wirelessly detected, the security server42 may retrieve the corresponding electronic calendars and habitualusage (as earlier explained). The security server 42 may then assign aphysical location based on this calendric and locational information. Asone example, if a majority of the invitees or members of a group arenearly co-located, the security server 42 may select a physical space inthe vicinity of the majority. However, if the invitees or group havespecial or unique space requirements (as illustrated with reference toFIGS. 35-38), a compatible physical space may be assigned. Personaldays, holidays, and other calendric entries may be used to dynamicallyreduce headcounts and, thus, physical needs. Impending weather events(perhaps as revealed by the weather data 249 illustrated in FIG. 21) mayalso be used to dynamically reduce headcounts and, thus, physical needs.

Intelligent notifications may be sent. Whenever any physical space isselected for any collaboration, people may be notified. This disclosure,for example, previously explained how the electronic message 80 may besent any user's destination device 82. Exemplary embodiments may thusadditionally or alternatively send the electronic message 80 whenalerting of a physical location assigned to a collaborative effort.Emails, text messages, and/or SMS messaging may be used to identifyworkspace assigned to a collaborative effort. Yet these electronicnotifications may themselves be intelligently dispatched. For example,if an employee only occasionally enters the building 22, then theelectronic message 80 may be sent detailing an assigned workspace forthat day. However, if a group habitually meets every Thursday in thesame physical location, exemplary embodiments may decline to send theelectronic message 80. Exemplary embodiments may simply decline toclutter or clog messaging inboxes with known, habitual informationdescribing a consistent work location. However, should the habitualroutine change, then exemplary embodiments may send notifications toalert of an atypical, new, or more optimal location. For example,maintenance efforts may force the group to meet in a different location.A special event may also force the group to meet in a differentlocation. Whatever the reason, exemplary embodiments need only notifywhen necessary or desired. Again, then, exemplary embodiments promoteconsistency in assignment.

Another example is provided. Suppose the security server 42 accesses thedatabase 70 of calendars and retrieves electronic information describingone or more electronic calendars of employees (perhaps as identified bytheir respective mobile device 30, as this disclosure explains). If anyof the electronic calendars have entries indicating an absence, then thepredictive module 382 may cause the security server 42 to infer orpredict that those employees will not need physical space (e.g., a deskor office) for the absent times of days. If any of those absentemployees are invitees to a meeting (as revealed by the database 46 ofmeetings), the security server 42 may infer or predict that those sameabsent employees will not be attendees to the scheduled meeting.Services may be reduced or even eliminated, as revealed by the database210 of services. The absentees may be noted or logged in the database350 of groups, thus perhaps further reducing any physical needs detailedin the database 370 of physical spaces. Perhaps electronic notificationsneed not be sent to the mobile devices of the absentees, as themessaging content may not be relevant for those not present. A simpleelectronic calendar entry, in other words, may cascade throughout thearchitecture for maximum efficiency of physical spacing.

Exemplary embodiments thus promote efficient and maximizedcollaboration. The entries in the electronic databases 44, 46, 70, 160,210, 300, 350, and/or 370 may be mined using data analytics to revealhabitual collaboration between people (based on wireless detection oftheir respective mobile devices 30). The locations of thesecollaborations may thus be matched with performance goals, productlaunches, and even sales figures. Exemplary embodiments, in other words,may be matched against performance metrics to determine whichcollaborations yield successful outcomes. As one example, some employeesmay repeatedly collaborate on products that generate a steady stream ormajority of revenues. Some physical locations may be better at spawningcreative, new ideas (such as objectively measured by patent filingsaccording to conference room, lobby, or other physical location withinthe building 22).

FIGS. 41-42 are flowcharts illustrating an algorithm for accessauthorization, according to exemplary embodiments. A unique cellularidentifier 110 is received (Block 400) and the security server 42 isnotified (Block 402). A database is queried for the cellular identifier110 (Block 404). Physical access to a secure area is granted, based on amatching entry in the database (Block 406). The electronic lock 90 maybe activated to permit entry (Block 408). The electronic notificationmessage 80 may be sent to a meeting organizer and/or other invitees,thus alerting to the arrival and access of the user associated with thecellular identifier (Block 410). The physical space 374 may also bedynamically determined, based on the membership 356 in the group 352(Block 412). An electronic reservation is generated for the physicalspace 374 (Block 414).

The flowchart continues with FIG. 42. Once the physical space 374 isknown, the corresponding route 162 may be retrieved (Block 416). Theelevator 94 may be summoned (Block 418). The corresponding services 216may also be retrieved (Block 420). Historical usage may be retrieved(Block 422). The future location 310 (Block 424) and/or the futurenetwork 312 (Block 426) may be predicted.

FIG. 43 is a schematic illustrating still more exemplary embodiments.FIG. 43 is a more detailed diagram illustrating a processor-controlleddevice 450. As earlier paragraphs explained, exemplary embodiments maypartially or entirely operate in any mobile or stationaryprocessor-controlled device. FIG. 43, then, illustrates the securityalgorithm 122 stored in a memory subsystem of the processor-controlleddevice 450. One or more processors communicate with the memory subsystemand execute either, some, or all applications. Because theprocessor-controlled device 450 is well known to those of ordinary skillin the art, no further explanation is needed.

FIG. 44 depicts other possible operating environments for additionalaspects of the exemplary embodiments. FIG. 44 illustrates the securityalgorithm 122 operating within various other processor-controlleddevices 450. FIG. 44, for example, illustrates that the securityalgorithm 122 may entirely or partially operate within a set-top box(“STB”) (452), a personal/digital video recorder (PVR/DVR) 454, a GlobalPositioning System (GPS) device 458, an interactive television 460, atablet computer 462, or any computer system, communications device, orprocessor-controlled device utilizing the processor and/or a digitalsignal processor (DP/DSP) 464. The device 450 may also include watches,radios, vehicle electronics, clocks, printers, gateways,mobile/implantable medical devices, and other apparatuses and systems.Because the architecture and operating principles of the various devices450 are well known, the hardware and software componentry of the variousdevices 450 are not further shown and described.

Exemplary embodiments may be physically embodied on or in acomputer-readable storage medium. This computer-readable medium, forexample, may include CD-ROM, DVD, tape, cassette, floppy disk, opticaldisk, memory card, memory drive, and large-capacity disks. Thiscomputer-readable medium, or media, could be distributed toend-subscribers, licensees, and assignees. A computer program productcomprises processor-executable instructions for dynamic assignment ofphysical space, as the above paragraphs explained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

The invention claimed is:
 1. A method, comprising: receiving, by aserver, a notification specifying a wireless device requesting an accessto a wireless network; determining, by the server, an identifierspecifying the wireless network; determining, by the server, a physicalspace that is associated with the identifier specifying the wirelessnetwork; and assigning, by the server, the physical space to thewireless device requesting the access to the wireless network specifiedby the identifier.
 2. The method of claim 1, further comprisingdetermining the wireless device is associated with a group of wirelessdevices.
 3. The method of claim 2, further comprising assigning thephysical space to the group of wireless devices.
 4. The method of claim1, further comprising determining a cellular identifier specified by thewireless device requesting the access to the wireless network.
 5. Themethod of claim 1, further comprising determining a cellular identifierspecified by the notification.
 6. The method of claim 1, furthercomprising generating a reservation associated with the physical space.7. The method of claim 1, further comprising generating a reservationassociated with the wireless device.
 8. A system, comprising: a hardwareprocessor; and a memory device, the memory device storing instructions,the instructions when executed causing the hardware processor to performoperations, the operations comprising: receiving a notificationspecifying a wireless device requesting an access to a wireless network;determining an identifier associated with the wireless network;determining a physical space that is associated with the identifier; andassigning the physical space to the wireless device requesting theaccess to the wireless network.
 9. The system of claim 8, wherein theoperations further comprise determining the wireless device isassociated with a group of wireless devices.
 10. The system of claim 9,wherein the operations further comprise assigning the physical space tothe group of wireless devices.
 11. The system of claim 8, wherein theoperations further comprise determining a cellular identifier associatedwith the wireless device requesting the access to the wireless network.12. The system of claim 8, wherein the operations further comprisedetermining a cellular identifier specified by the notification.
 13. Thesystem of claim 8, wherein the operations further comprise generating areservation associated with the physical space.
 14. The system of claim8, wherein the operations further comprise generating a reservationassociated with the wireless device.
 15. A memory device storinginstructions that when executed cause a processor to perform operations,the operations comprising: receiving a notification specifying awireless device requesting an access to a wireless network; determiningan identifier associated with the wireless network; determining aphysical space that is associated with the identifier; and assigning thephysical space to the wireless device requesting the access to thewireless network.
 16. The memory device of claim 15, wherein theoperations further comprise determining the wireless device isassociated with a group of wireless devices.
 17. The memory device ofclaim 16, wherein the operations further comprise assigning the physicalspace to the group of wireless devices.
 18. The memory device of claim15, wherein the operations further comprise determining a cellularidentifier associated with the wireless device requesting the access tothe wireless network.
 19. The memory device of claim 15, wherein theoperations further comprise determining a cellular identifier specifiedby the notification.
 20. The memory device of claim 15, wherein theoperations further comprise generating a reservation associated with thephysical space.